-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using PolySharp to allow use of C#13 #132
base: develop
Are you sure you want to change the base?
Conversation
Test Results: Windows 2 files 2 suites 4s ⏱️ Results for commit 8c4428c. ♻️ This comment has been updated with latest results. |
Test Results: Ubuntu 2 files 2 suites 5s ⏱️ Results for commit 8c4428c. ♻️ This comment has been updated with latest results. |
Test Results: MacOS 2 files 2 suites 5s ⏱️ Results for commit 8c4428c. ♻️ This comment has been updated with latest results. |
This introduces an untrusted third party dependency into a security critical library. It would be better to selectively port the individual Polyfills into core, then introduce a new dependency (and extend the chain of trust). |
Hi @iamcarbon and thanks for your raised concern. It's true that bringing in a dependency into any library should not be taken in lightly. This suggestion has been with the team for some time, and while we haven't committed to it yet, we want to explore the possibility of making such a change. We do believe measures can be taken to ensure stability and expected behavior. Rest assured, although the third party dependency in question appears to be well regarded, useful and stable, it won't be added without going through a due dilligence process. To you and anyone else reading this, please feel free to add your comments or any alternatives to move the SDK forward in this regard. |
Update target framework to .NET 9.0 Updated the target framework from .NET 6.0 to .NET 9.0. Added a commented-out section in the project file with instructions for testing against local changes to the YubiKey library, including a `ProjectReference` to a local YubiKey project file.
CryptographicOperations class duplicated in both Core and Yubikey
…c and remove duplicate implementation
…rtificate loading method
f41b4b1
to
4b413c4
Compare
…d remove old implementation
…mNumberGeneratorExt
@@ -88,7 +88,7 @@ public void AuthKey_Aes_Succeeds() | |||
0x51, 0x52, 0x53, 0x54, 0x55, 0x56, 0x57, 0x58 | |||
}; | |||
|
|||
var initCmd = new InitializeAuthenticateManagementKeyCommand(true, PivAlgorithm.TripleDes); | |||
var initCmd = new InitializeAuthenticateManagementKeyCommand(true, PivAlgorithm.TripleDes); // TODO this test only works with 5.4.3 and lower |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will handle this in test rework case
Yubico.YubiKey/tests/integration/Yubico/YubiKey/Piv/Commands/AuthMgmtKeyCmdTests.cs
Show resolved
Hide resolved
… for compatibility
…ation for project structure
…nd SmartCardDeviceListenerTests
…ject files" This reverts commit 85b35f0.
Description
This update removes the need for the Yubico.DotnetPolyfills-project. This project was adding a couple of methods, such as the Range and the Index operator. Now, since adding Polysharp, this is no longer needed as Polysharp generates polyfills for newer C# language features and APIs at compile-time. This also allows us to use C# language version 13 instead of 7.3.
Examples of new syntax can be seen here in a stowed away branch in this repo.
To anyone else reading this, please feel free to add your comments or any alternatives to move the SDK forward in this regard.
Fixes: YESDK1316
Type of change
How has this been tested?
Unit tests pass and builds pass.
Checklist:
dotnet format
to format my code